Queue management system and method

ABSTRACT

A queue management system in accordance with present embodiments may include a data server system including a processor and memory. The queue management system may include an interface system of the data server system configured to receive a reservation request including an indication of a general time period of arrival of a guest to an area. Additionally, the queue management system may include a reservation right allotment system of the data server system configured to correlate a reservation slot for accessing an attraction to identification information for the guest. Further, the queue management system may include a detection system of the data server system configured to determine when a portable identification feature associated with the identification information has arrived to the area, and a reservation assignment system of the data server system configured to establish a reservation to access the attraction at a specific time window.

FIELD OF DISCLOSURE

The present disclosure relates generally to the field of amusementparks. More specifically, embodiments of the present disclosure relateto methods and equipment utilized to control wait times in attractionqueues by providing reservations.

BACKGROUND

Since the early twentieth century, amusement parks have substantiallygrown in popularity. In order to address this increasing demand,amusement parks have been expanding at a tremendous rate by addingattractions and space. The addition of attractions (e.g., rides,restaurants, shops, and shows) generally provides an amusement park withadditional capacity to handle a larger number of guests. However, theadditional attractions also typically provide potential guests with anincentive to visit the amusement park. Thus, while a particularamusement park may add additional capacity, the additional capacity doesnot always result in reduced wait times for attractions because there isoften a corresponding increase in attendance. Further, due to operatingefficiencies, it is often desirable to limit the availability ofattractions during low attendance times. Thus, queuing for attractionsis a perennial issue for amusement parks.

While guests have demanded bigger, better, and more elaborateattractions, they also require and expect a positive overall experience.Providing a positive overall experience for amusement park guestsentails addressing certain issues related to queuing for attractions.Indeed, it is now recognized that park guests can be deterred fromreturning to a particular amusement park due to negative experienceswith queue waiting times. Further, guests may be prevented fromaccessing amusement park businesses (e.g., shops) due to time spentwaiting in queues. Indeed, in the past, guests have been forced to waithours in line to experience some of the more popular attractions at anamusement park. Additionally, it is now recognized that park capacitydoes not always equal guest utilization of that capacity due toindividual guest preferences for certain attractions over others.Accordingly, it is now recognized that it is desirable to improveamusement park queuing systems and methods.

DRAWINGS

These and other features, aspects, and advantages of the presentdisclosure will become better understood when the following detaileddescription is read with reference to the accompanying drawings in whichlike characters represent like parts throughout the drawings, wherein:

FIG. 1 is a schematic representation of an amusement park including areservation system in accordance with present techniques;

FIG. 2 is a process diagram of a method in accordance with presenttechniques;

FIG. 3 is a process diagram of a method in accordance with presenttechniques;

FIGS. 4A and 4B illustrate a process diagram of a method in accordancewith present techniques;

FIG. 5 is a process diagram of a method for facilitating guestscheduling of multiple reservations for attractions in accordance withpresent techniques; and

FIG. 6 is a process diagram of a method for coordinating guest schedulesin accordance with present techniques.

DETAILED DESCRIPTION

The present disclosure relates generally to methods and systems forcontrolling wait times in amusement park attraction queues bydynamically managing reservations for amusement park attractionsincluding shows, restaurants, rides, shops, and so forth. Presentembodiments include a system with an electronic data server andrespective applications capable of communicating and monitoring metricsor characteristics related to reservations for attractions in anamusement park, and controlling queue flow characteristics. The systemmay include a verification system, a tracking system, a redemptionsystem, mobile devices, and backend computers and devices. The systemmay be configured to receive one or more reservation requests at a timeand assign a general or specific time frame for the reservation based oninformation provided by a user and/or based on other data (e.g., dataregarding operation of a related attraction or data related to detectedlocations of guests holding reservations). Further, present embodimentsare configured to access or modify one or more existing reservationsand/or adjust queue characteristics (e.g., access ratios) based onchanges in the reservation requests, changes in guest scheduling, guestlocation, data regarding an attraction or attractions related to areservation, entitlement levels (e.g., based on tiered payment optionsfor various levels of access) and so forth. With regard to entitlementlevels, tiered approaches to pricing for various features or componentsmay be available, including micropayments for certain services or tasks.For example, a guest may provide a micropayment to receive periodicupdates regarding short queues in certain areas of the park.

The system may enable guests to utilize mobile or wireless technology towait in a virtual queue for a particular attraction or attractions whileexperiencing other attractions or relaxing in other areas in or awayfrom the amusement park. Indeed, present embodiments include a systemconfigured to communicate with one or more attractions related to areservation request or an existing reservation to dynamically adjust andoptimize guest waiting experiences in real-time, and communicate updatesto guests (e.g., via mobile or wireless technology). Present embodimentsmay facilitate communication with guests via portable communicationdevices, such as cellular telephones, pagers, and other wirelessdevices. Such devices may be referred to as mobile devices.Communications referenced herein between a system and guests includeemail, text, video, web-based, and audio communications from the systemto the mobile devices or the like. The location of guests within theamusement park may also be obtained by monitoring such mobile devices orother means (e.g. facial recognition systems, ticket scanning, etc.). Insome embodiments, communication with guests may be achieved via publiclyaccessible displays. For example, kiosks with communication features(e.g., computers capable of accessing a network) may be positionedthroughout the amusement park.

In accordance with present techniques, a reservation system isconfigured to provide an interface for a user or guest to make areservation for access to one or more attractions of an amusement parkduring a visit. Reservations may be made for a group of guests or asingle guest prior to arriving at the amusement park or while present inthe amusement park. Indeed, functions of the system described herein mayinclude communicating with a single guest or a group. Making areservation for multiple guests, as a group, may be facilitated byenabling association of all of the corresponding tickets with a singleguest's ticket. These reservations may be made prior to or during theguest's visit to the amusement park using a laptop computer, desktopcomputer, mobile device, or other access device. Such a reservation maybe acquired via on-line resources, via direct access to a portal of thereservation system, via a telephone system, and so forth.

In accordance with the present disclosure, tickets may include varioustypes or combinations of credentials that may be used to verify accessrights to an attraction (e.g., an amusement park). The tickets (e.g.,paper tickets, biometrics, or electronic tickets) may be utilized toverify access rights at a current time or future access rights. Whentickets are not purchased together, present embodiments may associatethe tickets as a group. This will allow any member of a group of gueststo acquire reservations for the group. For example, if a group ofseveral guests arrive at the amusement park and each separatelypurchases tickets, one of the group's guests can use present embodimentsto make one or more reservations for the group. Present embodiments arecapable of associating the reservation for the group with a singleticket, which becomes the “master ticket”. When the reservation isredeemed, the master ticket associated with the reservation must beconfirmed first and then the tickets of the remaining group members areconfirmed. Several techniques and systems may be utilized to associatetickets with a master ticket. This may include scanning the tickets toconfirm identification information, authenticity, and reservationinformation. During the confirmation process, each ticket may beassociated with the remaining reservations in the system. Accordingly,subsequent reservations may not require that the master ticket beconfirmed before a reservation can be used.

Further, reservations may be made prior to a guest visiting theamusement park without specifically designating a time frame for thereservation. For example, a reservation may be established for aparticular date without designating an hourly time range for thereservation. However, in some embodiments, an initial slot of time maybe defined based on a guest's predicted arrival time to the amusementpark. For example, this predicted arrival time may be designated as themorning or the afternoon. In such embodiments, once the guest arrives, aspecific time frame (e.g., 3:00 PM to 3:15 PM) may be assigned for thereservation depending on the guest's arrival time and the availabilityof reservation time slots for associated attractions. It should be notedthat present embodiments may be utilized to make multiple reservationsfor one or more attractions. Present embodiments may also facilitatecommunication between the reservation system and guests to provide fordynamic updating of reservation times and to provide crowd control byencouraging guests to visit particular areas of the amusement park.Further, present embodiments may efficiently accommodate schedulechanges of guests by facilitating reservation trading within thereservation system. For example, if a guest would prefer to change anassigned reservation, the guest may use the reservation system toacquire a new reservation at a more convenient time, returning theoriginal reservation to available inventory or reassigning it, ifapplicable.

Referring now to FIG. 1, a system for managing theme park attractionqueues is generally indicated by reference numeral 100. The queuemanagement system 100 includes a data server system 102, a guest entrysystem 104 (e.g., a ticketing system or access validating system), aredemption system 106, data readers 108, portable identificationfeatures (PIFs) 110, a tracking system 112, a backend computer system114, and at least one attraction 116. Certain components of the system100 may be extensions or modules of the data server system 102, andother components may be separate features that communicate with the dataserver system 102. Indeed, the data server system 102 may include one ornumerous computers with one or more processors 118 and memories 120(e.g., a hard drive or other tangible, machine-readable medium that arenon-transitory, which merely means that they are not signals). Indeed,in one embodiment, the data server system 102 includes one or moreredundant servers to ensure reliability and to enable maintenance. Thememory (or memories) 120 may store code or instructions that, whenimplemented by the processor (or processors) 118, cause the reservationsystem 100 to perform certain functions in accordance with presentembodiments. Indeed, certain component systems (e.g., the guest entrysystem 104) of the system 100 may include code stored in memory 120capable of being activated by a processor 118. It should be noted thatthe present disclosure may refer to a grouping of components of thesystem 100 or all of the components of the system 100 as the“reservation system 100” or the “system 100”. Thus, actions indicated asbeing performed by the reservation system 100 or system 100 may includeactions performed by a subset of the system 100. For example, the dataserver system 102 may coordinate with a data reader 108 of the guestentry system 104 to perform the action of determining whether aparticular guest has checked in (e.g., passed through an entry orportal) to the amusement park. This action may be referred to as havingbeen performed by the reservation system 100.

In the illustrated embodiment, the attraction 116 includes a monitoringand/or data maintenance system 122 that may be utilized to monitorand/or provide information regarding operation of the associatedattraction 116. These monitoring and/or data maintenance systems 122 maybe referred to as attraction systems 122 and may include one or more ofa computer, a control system, and monitoring features (e.g., sensors andcameras). In some embodiments, the attraction systems 122 basicallyinclude ports or workstations for entering information into, retrievingdata from, or otherwise communicating with the data server system 102.For example, the attraction systems 122 may enable employees of theamusement park to input data (e.g., wait times, attraction capacity, anddowntime) regarding operation of the related attraction. In otherembodiments, the attraction systems 122 are separate systems that areconfigured to operate independently and to communicate with the dataserver system 102. As an example, the attraction systems 122 may becapable of logging all activity (e.g., downtime, statistics regardingrequested and redeemed reservations, availability, and quantity oftraffic through the attraction) associated with reservations for thecorresponding attractions 116 to facilitate data analysis by the dataserver system 102 and/or the backend computer systems 114. In oneembodiment, the system 100 is capable of expansion to enable storage andprocessing of large amounts of data. Data obtained from the attractionsystems 122 may be submitted for data analysis by the system 100, theresults of which are used to assist with control of queuingcharacteristics and reservations, as will be discussed further below.

The PIFs 110 may include tickets. Specifically, for example, the PIFs110 may include printed tickets, biometrics, and/or mobile devices. Asan example, the PIFs 110 may include printed strips of material, facialrecognition, finger scans, cellular telephones, microchips (e.g., amemory) or circuitry installed in cards or bracelets, pagers, orwireless devices that can be provided by the amusement park or owned bythe guests. Indeed, a particular cellular telephone, which may be ownedby a guest or obtained from the amusement park, may be associated with aguest pass. The term guest pass may be used to generally refer to theright of a guest to access certain attractions or the amusement park ingeneral. For example, a guest pass does not necessarily have to be atangible item. A guest can purchase a guest pass, which is thenassociated with identification information (e.g., a password, serialnumber, name, or numeric code) of the guest on the system 100 such thatthe identity of the guest can be confirmed and the rights of the guestcan be ascertained. This association may be performed by a portableidentification feature assignment system of the data server system 102.Thus, a guest pass can be associated with a PIF 110 that is assigned toa particular guest, and the PIF 110 can then be used to confirm rightsof the guest via the system 100. Depending on this information, anamusement park employee or system can grant or deny a guest access tocertain attractions 116 or rights to make reservations. In someembodiments, the PIFs 110 are capable of wireless detection and provideaccess to identification information associated with the PIFs 110. Forexample, the tracking system 112 may employ device monitors 124 to trackPIFs 110 in the amusement park and identify the location of particularguests within a range of space. The system 100 also detects whether aguest has arrived in the amusement park by monitoring the guest entrysystem 104 and whether certain PIFs 110 associated with guests have beendetected. This may include scanning a ticket, scanning barcode from thescreen of a portable device, pinging a portable device, or the like,using the tracking system 112. Detection of entry of a guest into theamusement park may be confirmed at purchase of the guest pass andassociation with the PIF 110 by, for example, scanning the ticket orassociating identification information for a mobile device with a guestpass.

As indicated above, a guest (or agent of the guest) may use presentembodiments to obtain reservations to one or more attractions in orderto avoid or limit wait time in attraction queues, such as a queue 126for a particular ride 128. The system 100 may be designed to accommodatemaking, modifying, or accessing multiple reservations at one timewithout system slowdowns and with sufficient processing capability toensure adding additional capacity does not affect operational speed.Reservations through the system 100 may be acquired by a guest remotelyor from within the amusement park via an automated phone system 142, anInternet system 144 (e.g., a website or mobile site), a text messagingsystem 146, or a point-of-sale (POS) device system 148. The automatedphone system 142 is accessible from and includes a network of phones150. The Internet system 144 is in communication with the Internet 152and, in some embodiments, includes two separate websites, wherein afirst website accommodates guests wishing to make reservations and asecond website provides access for service representatives to performadministrative tasks in addition to make and revise reservations. Thetext messaging system 146 is in communication with a network of wirelessdevices 154 (e.g., cellular telephones). The POS device system 148includes and/or is in communication with POS devices 156.

The system 100 illustrated in FIG. 1 is capable of communicating withvarious different types of wireless or mobile devices, which may beowned by the guests or supplied by the amusement park. Indeed, the PIFs110 may include communication features that enable all guests withreservations to receive messages and updates from the system 100.However, a mobile device may be used for communication with the system100 without using the mobile device as a PIF 100. As an example ofsystem communications, a text message may be sent from the textmessaging system 146 to a mobile device functioning as a PIF 110 andassigned to a guest, wherein the text message indicates that aparticular reservation time has been moved back due to technicaldifficulties with a particular attraction. The text messaging system 146may be capable of sending a minimum of 20,000 automated text messagesper minute with delay notifications, information notifications,advertisements, and the like. Further, various other components of thesystem 100 may be capable of communicating wirelessly with mobiledevices or other wireless system components. For example, the datareaders 108 and POS devices 156 and so forth may be wireless devicesthat are capable of communicating with the data server system 102 in awireless manner. It should be noted that reference to mobile devicesindicates items that a guest can readily transport, such as a cellulartelephone, a pager, or the like.

When a guest is requesting a reservation right from offsite, as acomponent of the reservation process, the guest may be prompted by thesystem 100 (e.g., an interface module of the data server system 102) toprovide the system 100 with an estimated arrival time (e.g., morning orafternoon) to an area, such as to the amusement park or to a particularattraction 116 (e.g., a segregated area of the amusement park). Such arequest may be received through an interface system of the data serversystem 102 that is capable of receiving communications and input datafrom a guest (which includes current and potential patrons of theamusement park). Such communication may be provided via one or more ofthe automated phone system 142, the Internet system 144, the textmessaging system 146, or the POS device system 148. A specificreservation will not be established until the guest actually arrives.Rather, a reservation allotment system of the data server system 102sets aside a reservation slot based on the estimated arrival time andcorrelates the reservation slot to identification information for theguest. Providing an estimated arrival time may be required to establisha reservation right during the time period of the associated visit.

A detection system (e.g., the tracking system 112, the guest entrysystem 104, and/or the data readers 108) determines if the portableidentification feature has arrived at a designated area (e.g., theamusement park). If a guest fails to arrive during a predicted timeperiod (e.g., during morning hours), the system 100 may contact theguest and reschedule or cancel the associated reservation right based onfeedback from the guest and/or other criteria. Similarly, once a guestis confirmed to be present in the amusement park, a reservationassignment system of the data server system 102 may define a specificreservation time and the guest may be informed of the specificreservation time (e.g., a 15 minute window to arrive at the attraction116). For example, a guest that has an existing reservation right orthat has requested a reservation may receive text messages or recordedaudio messages from the system via one or more of the automated phonesystem 142, the Internet system 144, the text messaging system 146, orthe POS device system 148. As a specific example, upon checking in at akiosk including a POS device 156, the guest may be notified via the POSdevice system 148 that a specific time for a reservation has beenestablished by printing a message and the reservation time on a receiptproduced by the POS device 156. Similarly, communications from thesystem 100 may be provided via the automated phone system 142, theInternet system 144, or the text messaging system 146 to the guest viavoice messages, text messages, or emails sent to a mobile device and/orthe PIF 110 assigned to the guest (e.g., the guest's personalcommunication device or a device supplied by the amusement park). Thespecific time is narrower than the general time and will typically bedefined within the general time but may be later.

Additionally, the system 100 in the illustrated embodiment facilitatescommunication from the guests to the system 100. For example, a user maycommunicate that a reservation is no longer desired or that there willbe a delay in the guest's arrival to the amusement park or individualattraction 116 by submitting data to the system 100 via a mobile device,which may include the PIF 110. This type of information may be utilizedby the system 100 to manage the reservations of the guest and otherguests. Further, such information may be utilized by the system 100 tofacilitate queue management. For example, cancelations may be utilizedto adjust ratios of standby queues, express queues, very importantperson (VIP) queues, single rider queues, and reservation queues or anumber of guests allowed access via a reservation entry. Indeed, thesystem 100 may communicate such data to attraction control systems(e.g., attraction systems 122) or amusement park employees charged withqueue management. This may include provision of an access managementsystem of the data sever system 102 or attraction system 122 capable ofcontrolling an adjustable ratio variable that adjusts certain queuecharacteristics (e.g., number of standby line entries) relative toreservation entries to maintain a desired wait time, and capable ofproviding information regarding nearby attractions with low wait times(e.g., the nearest attraction with a lower wait time than thereservation queue or the lowest wait time).

Communications to the system 100 from guests may include periodicupdates regarding respective locations of the PIFs 110 or updatesentered by the guests via a data entry component of the each of the PIFs110. As an example, the PIFs 110 may include global positioning systems(GPS), radio frequency identification (RFID) tags, or other detectablefeatures that can be used to determine locations of the PIFs 110.Specifically, for example, if a PIF 110 is scanned as part of a purchasedetected by a data reader 108, or detected by a device monitor 124positioned in the amusement park, such information may be employed todetermine a general location of the guest with which the system 100 hasassociated the PIF 110. Further, a guest may be able to submit requestsor updates via a data entry feature (e.g., keyboard or other interfaceof the PIF 110). For example, the PIFs 110 may each include a keyboardor a basic input that enables a guest to respond affirmatively ornegatively to questions issued by the system 100, such as questionsregarding whether the guest intends to be present for a pendingreservation. Other mobile devices not being employed as PIFs 110 mayalso be used to communicate with the system 100.

In addition to communications regarding reservations, communicationsbetween the system 100 and a guest may include other types ofinformation or data, such as information related to crowd flow throughthe amusement park. For example, the system 100 may utilize locationdata from the PIFs 110 and other sources to assemble crowd flow data.This data may then be employed by the system 100 to encourage guestdistribution throughout the amusement park, thus reducing crowds. Forexample, an electronic coupon, which may be limited to certain guests byidentification information, for a nearby attraction may be issued by thesystem 100 via the PIFs 110 or a notice may be distributed indicatingthat short waits are available at certain attractions. The system 100 iscapable of pushing information (e.g., coupons, advertisements, and waittimes) out to guests via a web portal or the like. Specifically, forexample, the system 100 may send out a text message to all park patronsthat have a PIF 110 with particular identification information that willallow these park patrons to receive a discount at a shop or restaurant.Further, the system 100 may track usage of these discounts such that thesystem 100 is aware of time and location of use, which can be used forcrowd control (e.g., submission of additional notifications based onlocation, item purchased, and so forth). Additionally, the system 100may automatically adjust reservations based on location andavailability. For example, a reservation may be adjusted because apatron is located too far away from the attraction (e.g., as determinedby a purchase time of an item) to reach the associated attraction intime for the reservation or a guest's place in line may be adjustedbecause the guest was delayed in a restaurant due to slow service.

As with other types of information discussed above, the system 100 maycommunicate crowd flow information between attractions 116 anddynamically adjust queue characteristics (e.g., admission ratios betweenreservations and standby lines) to move toward optimization of guestwaiting times for the attractions. For example, adjustments may be madeto a ratio of guests allowed to enter a queued souvenir shop 160 from astandby line 162 (e.g., an area in which guests line up to enter anattraction without a reservation) relative to guests allowed to enterthe souvenir shop 160 from a reservation line 164 (e.g., an area inwhich guests line up to enter an attraction based on a reservation)based on remaining reservations to enter the souvenir shop 160 andavailability of access to attractions throughout the amusement park. Itshould be noted that guests entering the reservation line 164 mayconfirm a right to enter the reservation line or queue 164 by allowing adata reader 108 access to an associated PIF 110, and may confirm accessto entering the souvenir shop 160 by allowing a different data reader108 access to the associated PIF 110. Thus, the data reader 108 isutilized as an entry access confirmation feature. This dual confirmationmay be utilized to monitor queue wait times. Similarly, a data reader108 may be employed as an access confirmation feature by confirming thata guest has entered an attraction (e.g., entered a ride vehicle of anattraction).

The system 100 may also facilitate guest-to-guest communications andsystem-directed communications based on common characteristics ofcertain guests. Specifically, present embodiments may collectdemographic data during a registration process or through an opting inprocess. A registration process may include a data entry requirement orany utilization of the system 100 by a guest that facilitatesacquisition of the demographic data. For example, registration mayinclude utilization of a cellular telephone by a guest in conjunctionwith the system 100, and the acquired demographic data may include anarea code of the phone number associated with the cellular telephone.Direct guest-to-guest communication may be established between PIFs 110assigned to the guests via the system when the PIFs 110 are capable ofcommunication, or direct guest-to-guest communication may be establishedbetween communication devices provided by the guests or park and knownby the system 100. Similarly, such communication may be established viaenabling access to social media, which may also employ the PIFs 110 orknown communication devices. Accordingly, guests with commoncharacteristics based on their registration data or selected option canprovide notices to one another. For example, guests from a similargeographic region may notify each other of activities that might be ofcommon interest. Similarly, the system 100 may provide informationregarding activities that may be of common interest based on demographicdata. Among other things, the system 100 may facilitate posting statusupdates, notifying guests in a certain group of activities relevant tothe group, or providing notice of certain conditions in the park.

In one embodiment of the present disclosure, a PIF 110 (e.g., an RFIDtransponder) is provided to each guest or group as they enter theamusement park. This may include the amusement park renting, loaning, orsimply selling the PIFs 110 to guests. Each PIF 110 may be programmedand assigned in the system 100 to uniquely identify each guest or group.In some embodiments, providing each guest with a PIF 110 may includeinstructing the system to recognize and/or communicate with a deviceowned by a guest such that the device owned by the guest is employed andactivated by the system 100 as a PIF 110. For example, the system 100may be used to download an application onto a guest's cellular telephonesuch that the system 100 associates the guest's cellular telephone withan amusement park ticket and with the guest (or a group). In anotherembodiment, the system 100 may be programmed to detect the PIF 110 andrecognize association with a valid guest pass. Further, as discussedabove, different types of PIFs 110 may include paper or plastic ticketsor bracelets with integral detection devices. For example, braceletsthat include integral circuitry that stores a unique identifier in amemory and/or provides communication capabilities (e.g., the ability tocommunicate with a global positioning unit or other positional detectionsystem). Automatic identification and data capture (AIDC) devices suchas RFID tags may be used, for example. Other features of PIFs 110 usablewith present embodiments may include barcodes, magnetic strips, pinnumbers, cellular telephone identifiers, hotel room keys, credit cards,combinations thereof, and so forth. Any identification components of thePIFs 110 or combinations of such devices may have a reciprocal readerthat communicates with the data readers 108 or other guest identifiers(e.g., POS devices 156) to track movement and/or spending of guests inand/or around the amusement park. This enables tracking of crowd flow.Furthermore, in some embodiments, the PIFs 110 include handheldelectronic devices with display screens that enable communicationsregarding crowd flow to facilitate directing of guests to certain areasof the park.

In one embodiment, the system 100 is capable of controlling access andmanaging reservations to attractions 116 by facilitating communicationbetween the data server system 102, which serves as a central queuecontrol system, and the guest entry system 104. Indeed, coordinationbetween the data server system 102 and the guest entry system 104facilitates identification of the arrival and presence in the amusementpark of guests with reservations, which assists with the management ofreservations. Indeed, reservations may be changed or canceled dependingon an algorithm that takes arrival time to the amusement park intoaccount. Communication of the arrival and/or presence of a guest may beachieved by polling the guest entry system 104 with the data serversystem 102 at certain intervals (e.g., every 30 or 60 seconds) or atcertain times, or by sending identification data for the associated PIF110 from the guest entry system 104 to the data server system 102 eachtime a guest is admitted to the amusement park via the guest entrysystem 104. For example, the data reader 108 associated with aparticular attraction 116 may communicate with the data server system102 or directly with the guest entry system 104 to confirm that a guesthas a valid park entry ticket. Specifically, for example, a guest maysupply the PIF 110 assigned to the guest to the data reader 108 for aparticular attraction 116. The data reader 108 may then acquireinformation from the PIF 110 and communicate with other systemcomponents to confirm that the PIF 110 is associated with a validreservation and that the PIF 110 is known to be properly present in theamusement park. This may include confirming that the PIF 110 (e.g., acellular telephone) has been identified as entering the amusement park(e.g., scanned during entry) via the guest entry system 104 and that thePIF 110 has been associated with a reservation for the particularattraction 116 or any attraction 116. In some embodiments, a guest mustuse the PIF 110 to communicate with a first data reader 166 in order toenter the queue 164 and then use the PIF 110 to communicate with asecond data reader 168 to enter the attraction 116. This may facilitatemonitoring of queue characteristics.

In one embodiment, the system 100 enables making a reservation for anindividual or a group to access an attraction during a time range,modify the reservation, delay the reservation (e.g., delay thereservation at five minute intervals), transfer a reservation from onePIF 110 to another (e.g., from one group member to another), cancel areservation, and provide reservation details and updates (e.g., inreal-time). As indicated above, the system 100 includes numerous accessor interface points that are capable of interfacing with a commercemanagement system (e.g., a module of the data server system 102 or aseparate system in communication with or accessible through the dataserver system 102) for the amusement park. Indeed, users can access orinterface with the system 100 remotely or from the amusement parkproperty via the automated phone system 142, the Internet system 144,the text messaging system 146, or the POS device system 148. In someembodiments, accessing and manipulating reservations may be achievedusing the PIF 110, which may be used to communicate with the data serversystem 102. Indeed, a guest may request that a reservation be moved back(e.g., moved back thirty minutes) or canceled by sending a text messagefrom the PIF 110 or a system-recognized communication device to the dataserver system 102 because the guest took more time than expected havinga meal. All interface points may be assigned the same capabilitiesdepending on available security. For example, if it is determined thatthere is a risk of losing financial data during a transaction because oflimited security from the interface point, access from such an interfacepoint may be limited. Further, access to the system 100 to acquirereservations may be limited depending on the purchase of access rights.For example, a guest may have to purchase a reservation ability tosuccessfully make reservations via the system 100. However, the purchaseprice of the reservation ability may be set to zero or a purchasing stepmay be bypassed. When the purchasing step is bypassed, the acquiring ofreservations will seamlessly operate such that no indication of arequired payment is provided. It should be noted that, in order toaccess the system 100 and make a reservation that requires access to aparticular area or attraction (e.g., amusement park) as a precursor, auser can be required to have already purchased a ticket for theattraction or group of attractions. Indeed, access to makingreservations within the system 100 or access to the system 100 itselfmay be limited to users that own a corresponding ticket or to those withspecial access (e.g., theme park employees).

FIGS. 2 and 3 include process flow diagrams for a procedure inaccordance with present embodiments. The process is generally indicatedby reference numeral 200 and includes various blocks that representactions or steps of the process 200. The process 200 may be controlledor facilitated by a system, such as the data server system 102 and/orother components of the system 100, in accordance with presentembodiments. Indeed, in one embodiment, the data server system 102includes the processor 118 and the memory 120, wherein the memory 120stores instructions implemented by the processor 118 to receive inputsof data, manipulate the associated data to transform the inputs intoassembled information, and provide outputs corresponding to processsteps or actions disclosed herein. Components of the process 200 may beperformed by the data reader 108, which may maintain its own dataprocessing capabilities, or other components of the system 100. Further,in different embodiments, certain actions or steps may be performed in adifferent order.

As illustrated in FIG. 2, the process 200 begins with a determination ofwhether a ticket or multiple tickets have already been purchased, asrepresented by block 202. In this context, a ticket is a right to accessthe amusement park or an attraction 116 of the amusement park. In othercontexts, the ticket may be associated with different access rights. Asan example, acquiring a ticket may include having the identity of aguest associated with such a right in the system 100. Specifically, forexample, a guest may be assigned and provided a guest identificationnumber, and the system may store information in memory identifying thatnumber with a right of access. If tickets have not been purchased, theprocess 200 facilitates purchasing of tickets, as represented by block204. In accordance with present embodiments, this purchase of a ticketor tickets is coordinated via the POS device system 148 (e.g., a ticketbooth), via the Internet system 144, or via the automated phone system142. During purchase, an attraction reservation capability may be addedto a purchased ticket or multiple purchased tickets, as represented byblock 206. The attraction reservation capability may be automaticallyadded in some embodiments as a free component of the ticket. In otherembodiments, the attraction reservation capability may be auser-selected option, which may be free or may require an additionalfee. The system 100 is capable of giving certain reservations priorityover other reservations. Priority may be given to guests that pay extra,very important persons, or guests that perform special tasks.

Block 206 may also represent the actual addition of one or moreattraction reservations at the time of purchasing the ticket or tickets,which may include establishing a procedure for communicating informationabout the reservation. Indeed, block 208 represents prompting a guest toindicate whether a mobile device is available. If the guest does nothave access to such a device, the guest may be directed to acquirealternate communication capabilities (e.g., self-provided communicationdevice or park-provided communication device), as represented by block210. To facilitate this, the guest may be directed to communicate withguest services. Accordingly, guest services can arrange for provision ofa mobile device to the guest for purposes of communicating informationabout reservations and potentially serving as a PIF 110. If the guestwould prefer not to use such a mobile device, arrangements can be madefor other types of notification and confirmation, such as via kiosksthroughout the amusement park and paper tickets. Returning to the promptprovided in block 208, if the guest has a mobile phone, a mobilecommunication device assigned by the amusement park, or the like, theguest can indicate that such a mobile device is available. In thisevent, the guest may be further prompted to provide access to the mobiledevice via a phone number, email address, or the like, as represented byblock 212. For example, a guest may provide a phone number that can beused by the system 100 for text or voice communications related toattraction reservations. Indeed, the guest may actually select desiredtypes of notifications, as represented by block 214. This may includeselecting whether audio and/or text notifications are sent. The system100 may prompt the guest to indicate whether text messages areacceptable. If the guest prefers not to use text, automated voicemessages may be used. Further, block 214 may represent allowing a guestto determine whether certain types of information are sent to the mobiledevice. For example, a guest may limit communications to communicationsthat are related to established reservations such that the guest doesnot receive communications related to coupons, wait times at other areasof the park, and so forth. In some embodiments, certain types ofinformation may be accessed, received, or controlled based on a pricingtier of purchased access rights. For example, a guest with an upper tieraccess right may receive or access exclusive information about eventsonly available to those with such access rights. As another example,those with upper tier rights may be able to block certain communications(e.g., advertisements) that cannot otherwise be blocked.

Once the manner of communication between the system 100 and the guesthas been established, the process 200 continues to establish details ofa reservation. As represented by block 216, this may include selectingan attraction, a reservation date, and a general time for thereservation. In some embodiments, only one attraction and/or reservationdate is available for reservation, and, thus, an attraction and/or datedo not need to be selected. Present embodiments allow a user to make areservation prior to entering the park to confirm access to a particularattraction. However, the specific time of the reservation may not bemade until the guest actually enters the amusement park. Indeed, forexample, the specific time of a reservation may not be made until afterthe ticket associated with the reservation is identified by the guestentry system 104.

In the illustrated embodiment, the guest is requested by the system 100to provide a general time for a reservation, as illustrated by block216, to assist with organization of reservations. As previously noted,the actual reservation time will not be established until certaincriteria are met. For example, a specific time window (e.g., a 15 minutewindow of time) for the reservation may not be established until theguest is confirmed to be present in the amusement park and has confirmedthat the reservation is still desired. The general time for thereservation may be indicated as morning, afternoon, or evening. Inanother embodiment, the general time for the reservation may be one ofvarious windows of time (e.g., four hour windows of time) that can beselected by the guest. This indication of a general time may allow forflexibility within the reservation system 100. For example, if a guestindicates a general time for the reservation to be in the morning of aparticular day, a determination may be made regarding whether a guesthas actually arrived at the park by a certain time in the morning. Ifthe guest has not arrived, the guest may be contacted via the mobiledevice, which may include a PIF 110, to determine whether an adjustmentto or cancelation of the reservation should be made. Certain adjustmentsto or cancelations of reservations may be automatically made when aguest has not arrived within an indicated window of time, when a guestfails to respond via the mobile device, when a guest provides certainupdates (e.g., “will be one hour late”), or the like. As a specificexample, when a guest has not arrived by a time that corresponds to thetime set as the general time for the reservation, the guest may beprompted to indicate whether the guest still plans on visiting theamusement park. If the guest still plans on visiting the amusement park,the reservation may be adjusted. If the guest is no longer planning tovisit the amusement park, the reservation may be canceled. When areservation is adjusted, other reservations may be moved as well.Further, if a reservation is canceled, other reservations may be movedaround and those in an alternate list may be contacted to fill theavailable reservation slot.

The present system 100 allows for multiple reservations to be made atone time. In one embodiment, multiple reservations may be made andinitially associated with a single ticket or with each of multipletickets. Indeed, in addition to receiving the other information providedin block 216, block 218 represents receiving an indication of a numberof guests for the requested reservation. By allowing multiplereservations to be associated with a single ticket, a single groupmember may make reservations for a group of guests. However,reservations of more than a certain number of guests (e.g., 10 guests)may require approval from amusement park personnel (e.g., a member of agroup sales department). Accordingly, block 218 represents receiving aninput regarding a number of guests for which the reservation is to bemade, which may include indicating that the reservation is for a singleguest. Next, as represented by block 220, a determination is made as towhether the reservation is for a group larger than a certain threshold.If the group exceeds the threshold, the guest may be directed to contacta group sales representative for the amusement park or the like, asrepresented by block 222. This may include automatically connecting theguest via phone or initiating an email to the appropriate contact.

If the group does not exceed the threshold designated for groupreservations (e.g., the reservation is for a single guest), the process200 continues to a determination of whether the attraction for which thereservation has been requested has sufficient capacity, as indicated byblock 224. In one embodiment, this action may include communicationbetween the data server system 102 and the attraction system 122. Forexample, as discussed above, each attraction 116 may include monitoringand/or status management features (e.g., attraction computers) thatmaintain information regarding reservation times, availability,downtime, and the like. In other embodiments, all of this informationmay be centrally located (e.g., stored on the data server system 102).If a determination is made that there is sufficient capacity for therequested reservation or reservations, confirmation of the reservationor reservations may be provided to the guest and the reservation isbooked, as represented in block 226, and the reservation is booked inthe data server system 102 and/or the management system or attractionsystem 122 for the particular attraction 116 for which the reservationwas made. For example, confirmation may include a text message, email,printout, or audio message transmitted from the data server system 102to the mobile device via the POS device system 148, Internet system 146,the phone system 142, or the text messaging system 146. In otherembodiments, the confirmation may simply be provided via the devicebeing employed to make the reservation.

If a determination is made that there is insufficient capacity toaccommodate the requested reservation, the process may prompt the guestto select another date, a different time period, or a differentattraction, as represented by block 228. In some embodiments, if thegroup size can be reduced or divided to enable reservations, the guestmay be notified of options for dividing the group or reducing the sizeof the group to obtain available reservation slots. If the guest choosesto make changes to the requested reservations, the process returns toblock 216. If the guest chooses not to revise the request, the guest isprompted to select whether placement in an alternate list (a queue forfilling slots that become available) or cancellation of the reservationrequest is desired, as represented by block 229. The prompt in block 229may make clear that not selecting placement in an alternate list resultsin cancellation. The requested reservation may be placed in an alternatelist when that option is selected, as represented by block 230. Indeed,present embodiments include a waiting list function such that whenreservations are not available, the guest can obtain a position in awaiting list for notification of potential reservation slots that becomeavailable. Once the guest or group is assigned a position in thealternate list, the guest may be notified that the reservation has notbeen booked but that the guest and/or group has been assigned a slot inthe alternate list, as represented by block 232. If the guest choosescancellation, the reservation request is simply canceled and the guestis notified, as represented by block 234. As with confirmation ofreservations, as discussed above, notification may be achieved bysubmitting a text message or voice mail to the mobile device or bycommunicating via the device being employed to request reservations.Further, should an opening for a reservation become available, the guestor group may be notified of the opening via the mobile device or viaother notification mechanisms. The guests may be requested to respond tosuch notification by indicating whether they can fill the slot or not.The guest may be able to respond via the PIF 110 assigned to the guest.If the guest indicates availability to take the open reservation slot,the wait list reservation may be moved into the open reservation slot.

Returning to block 202 of the process 200, if tickets have already beenpurchased, the process 200 may be directed to contacting the reservationsystem 100, as represented by block 250 in FIG. 3. Upon accessing thereservation system, the guest may be prompted to confirm identificationof the guest or group, as represented by block 252. This may includeentering a confirmation number, scanning a physical ticket, accessing anapplication on a mobile device, or the like. Next, as represented byblock 254, a determination is made as to whether the identificationinformation corresponds to a guest pass that is currently valid or inservice. If the identification information does not correspond to avalid guest pass, the process directs the user to guest services, asrepresented by block 256. This may include automatically connecting theguest to amusement park personnel via phone or automatically generatingan email directed to the amusement park personnel.

If the system 100 determines that the identification informationcorresponds to a valid guest pass, a determination may be made as towhether the guest has previously associated the guest pass with a mobiledevice. If a mobile device has not been associated with the guest, theprocess 200 continues to block 258, which represents determining whethersuch a device is available. Many of the following steps are essentiallyequivalent to steps indicated and described with respect to FIG. 2.Specifically, block 258 represents prompting a guest to indicate whethera mobile device is available. If the guest does not have access to sucha mobile device, the guest may be directed to guest services, asrepresented by block 260. Accordingly, guest services can arrange forcommunications capabilities for the guest by, for example, provision ofa mobile device to the guest for purposes of communicating informationabout reservations. If the guest would prefer not to use such a mobiledevice, arrangements can be made for notification via kiosks throughoutthe amusement park or the like.

Returning to the prompt provided in block 258, if the guest has a mobilephone, a mobile communication device assigned by the amusement park, orthe like, the guest can indicate that such a mobile device is available.In this event, the guest may be further prompted to provide access tothe mobile device and then provide such access via a phone number, emailaddress, or the like, as represented by block 262. For example, a guestmay provide a phone number that can be used by the system 100 for textor voice communications related to attraction reservations. Indeed, theguest may actually select types of notifications, as represented byblock 264. This may include selecting whether audio and/or textnotifications are sent. The system 100 may prompt the guest to indicatewhether text messages are acceptable. If the guest prefers not to usetext, automated voice messages may be used. Similarly, emails may beprovided as an option. Further, block 264 may represent allowing a guestto determine whether certain types of information are sent to the mobiledevice. For example, a guest may limit communications to those relatedto reservations such that the guest does not receive communicationsrelated to coupons, wait times at other areas of the park, and so forth.It should be noted that, if a mobile device has already been identifiedat block 254, the process 200 may continue directly to block 264 or 266.

Once the manner of communication between the system 100 and the guesthas been established, the process 200 continues to establishing detailsof a reservation. As represented by block 266, this may includeselecting an attraction, a reservation date, and a general time for thereservation. In some embodiments, only one attraction is made availablefor reservation, and, thus, an attraction does not need to be selected.As noted above, present embodiments allow a user to make a reservationprior to entering the park to confirm access to a particular attraction.However, the specific time of the reservation may not be made by thesystem 100 or provided to the guest until the guest actually enters theamusement park. Indeed, for example, the specific time of a reservationmay not be made until after the ticket associated with the reservationis identified by the guest entry system 104.

A general time (e.g., morning or afternoon) for a reservation may berequested by the system 100, as illustrated by block 266, to assist withorganization of reservations. The general time for the reservation isindicated as morning, afternoon, or evening. In another embodiment, thegeneral time for the reservation may be one of various windows of timethat can be selected by the guest. This indication of a general time mayallow for flexibility within the reservation system 100. If the guesthas not arrived by a time corresponding to the indicated general time,the guest may be contacted via the mobile device or the like todetermine whether an adjustment to or cancellation of the reservationshould be made. Certain adjustments to or cancelations of reservationsmay be automatically made when a guest has not arrived within anindicated window of time, when a guest fails to respond via the mobiledevice, when a guest provides certain updates, or the like. When areservation is adjusted, other reservations may be moved as well.Further, if a reservation is canceled, other reservations may be movedaround and those in an alternate list may be contacted to fill theavailable reservation slot.

As when purchasing tickets, as illustrated in FIG. 2, the present system100 allows for multiple reservations to be made with respect to ticketsthat have already been purchased. Indeed, in one embodiment, multiplereservations may be made and initially associated with a single ticketor with each of multiple tickets. By allowing multiple reservations tobe associated with a single ticket, a single group member may makereservations for a group of guests. However, reservations of more than acertain number guests may require approval from amusement parkpersonnel. Accordingly, block 268 represents inputting a number ofguests for which the reservation is to be made, which may includeindicating that the reservation is for a single guest. Next, asrepresented by block 270, a determination is made as to whether thereservation is for a group larger than a certain threshold. If the groupexceeds the threshold, the guest may be directed to contact a groupsales representative for the amusement park or the like, as illustratedby block 272. This may include automatically connecting the guest viaphone or initiating an email to the appropriate contact.

If the group size is within the threshold, a determination is made withregard to capacity in the attraction, as represented by block 276. If adetermination is made that there is insufficient capacity to accommodatethe requested reservation, the process 200 includes prompting the guestto select another date, a different time period, or a differentattraction, as represented by block 278. In some embodiments, if thegroup size can be reduced or divided to enable reservations, the guestmay be notified of options for dividing the group or reducing the sizeof the group to obtain available reservation slots. If the guest choosesto make changes to the requested reservations, the process returns toblock 266. If the guest chooses not to revise the request and choosesnot to cancel the request, the requested reservation may be placed in analternate list, as represented by block 280. Indeed, present embodimentsinclude a waiting list function such that when reservations are notavailable, the guest can obtain a position in a waiting list fornotification of potential reservation slots that become available. Oncethe guest or group is assigned a position in the alternate list, theguest may be notified that the reservation has not been booked by thatthe guest and/or group has been assigned a slot in the alternate list,as represented by block 282.

If a determination is made that there is sufficient capacity for therequested reservation or reservations, a determination is made regardingwhether the guest or guests have already accessed the attraction withina time period (e.g., on the date of the requested reservation, within amorning time period, or the like), as indicated by block 290. If theguest has previously experienced the attraction with the designated timeperiod, a determination is made in block 292 as to whether a thresholdamount of access has been reached (e.g., whether the guest or group hasexperienced the attraction three times in the same day). Such adetermination may be made by an access management feature (e.g., asystem of the data server system 102 or the system 122). If there is nolimit or the limit has not been reached for accessing the attraction,confirmation of the reservation or reservations may be provided to theguest or group, as represented in block 294, and the reservation isbooked in the data server system 100 and/or the management system 122for the particular attraction 116 for which the reservation was made.However, subsequent access to an attraction may be limited based onprevious access. If there is a limit on a number of times guests canaccess the attraction within the time period and that limit has beenreached, access to another reservation may be denied, and the guests maybe placed in an alternate list, as indicated by block 280. For example,confirmation may include a text message or audio message transmittedfrom the data server system 102 to the mobile device via the Internetsystem 144, the phone system 142, the text system 146, or the POS devicesystem 148.

FIG. 4 is a process flow diagram of a method of employing the system 100in accordance with present embodiments. The process is generallyindicated by reference numeral 400 and includes various blocks thatrepresent actions or steps of the process 400. The process 400 may becontrolled or facilitated by a system, such as the data server system102 and/or other components of the system 100, in accordance withpresent embodiments. Indeed, in one embodiment, the data server system102 includes the processor 118 and the memory 120, wherein the memory120 stores instructions implemented by the processor 118 to receiveinputs and provide outputs corresponding to process steps or actionsdisclosed herein. These inputs and outputs may be respectively receivedfrom and directed to other components of the system 100 with respect tothe data server system 102. Further, in different embodiments, certainactions or steps may be performed in a different order.

Inputs to the system 100 from a guest (before or during the guest'svisit) may include a ticket identification, a mobile phone number, areservation date, a reservation group size, estimated park entry time(e.g., morning or afternoon), associated ticket identifications (e.g.,group ticket information), and so forth. Inputs to the system 100 fromoperators may include data indicative of ride capacity, downtimeestimates, operational status of an attraction, re-ride status, queueratio, messages, advertisements, statistics, and data requests.Automated inputs may include guest park entry time, guest queue entrytime, guest queue exit time, standby time estimate, and valid ticketconfirmation. Outputs from the system 100 to various systems (e.g.,website, mobile site, text messaging system, phone, and POS devices) mayinclude reservation capacity check results, general messaging,advertisements, available reservation dates, and reservationconfirmations. Outputs from the system 100 to operators may includeallowed ride queue entry messages and reservation approved messages.Outputs from the system 100 to guests may include status updates,reservation modification messages, reservation window messages, timelimit warnings, active time window messages, guest-appreciationmessages, confirmation of reservations, updates regarding reservations,general messaging, advertisements, and park entry messages. In differentembodiments, certain inputs and outputs may be directed to differentcomponents.

The process 400 begins with confirming that a guest has appropriateaccess rights and allowing the guest to enter the amusement park whenthe access rights are confirmed, as represented by block 402. This stepmay involve the use of the guest entry system 104. Access rights may beconfirmed by determining that the guest has provided identificationinformation (e.g., a bar code on a physical ticket or data stored on amobile device) that corresponds to a valid right to access the amusementpark. For example, this may include scanning a ticket provided by theguest and confirming that the information retrieved from the ticket hasbeen stored in a central database as corresponding to a right of entryon the date of scanning. Indeed, such information may be stored on thecentral database 102 and issued to the guest electronically or on aphysical ticket item at the time of purchase.

After the identification information is confirmed, a determination ismade with regard to whether the identification information is associatedwith an attraction reservation, as represented by block 404. If noreservation has been associated with the identification information, asrepresented by block 406, the guest may use standby lines to accessattractions, join a group that has group reservations, or acquire areservation. For example, if a guest did not establish reservationsprior to arriving at the amusement park, the guest may use the Internetsystem 144, phone system 142, text system 146, or the POS device system148 to obtain reservation rights and/or make reservations. If one ormore reservations are already associated with the identificationinformation and certain criteria are met, the system 100 automaticallyestablishes specific reservation times, as represented by block 408.Indeed, once the guest is identified as being present in the amusementpark, as occurs at block 402, the general time associated with theestablished reservation is converted into a more specified time (e.g., atime window or general time at which the attraction can be accessed withthe reservation) and the guest is provided with a notification (e.g., avoice message, text message, or email) of the reservations via themobile device or the like, as represented in block 410. As a specificexample, upon requesting a reservation, the guest may provide a broadwindow of time such as “during morning operation hours,” “duringafternoon operation hours,” “during evening operation hours,” “between1:00 PM and 6:00 PM,” “between 7:00 AM and Noon”, and so forth. Uponconfirming the guest's entry into the amusement park, upon confirmingthat the guest is present in a certain area, or upon the guest checkingin, a specific time for the reservation may be assigned by the system100, such as a window of time from 2:00 PM to 2:15 PM or approximately3:00 PM. This may not automatically occur when certain criteria are notmet. For example, if the guest does not arrive within the predefinedtime frame (e.g., morning or afternoon), the availability of thereservations may have changed. As another example, the attraction may beunavailable due to technical difficulties. If there are issues with thereservation, these may also be communicated to the guest in the samemanner as confirmation of reservations would be communicated.

Once reservations are confirmed, the system 100 may prompt the guest tomake available an option to cancel or modify the reservations, asrepresented by block 412. For example, immediately after notifying theguest of confirmed reservations, the system 100 may request that theguest indicate whether certain reservations should be canceled ormodified. If the guest indicates that reservations should be modified orcanceled, as represented by block 414, the guest may be directed toguest services or to a component of reservation system 100 thatfacilitates performing the component of the process 200 set forth inFIG. 3. If the guest does not wish to change any reservations, thereservations may be transferred to other identification information(e.g., identification information associated with a PIF 110 assigned toanother guest). For example, a guest with a ticket associated with aparticular reservation can transfer the reservation to the ticket ofanother guest. Indeed, the system 100 may prompt a user or receive auser request to transfer reservations, as illustrated by block 416. Theguest may respond by using the mobile device, a kiosk, contacting guestservices, or the like to transfer the reservation to the identificationinformation for another access pass, as represented by block 420.Numerous reservations may be transferred at once or a series oftransfers may be performed in a loop operation, as indicated by thearrow pointing from block 420 to block 416, until the desired transfershave been completed. It should be noted that the system 100 may allowguests to change or modify reservations within certain time windows(e.g., at least 30 minutes before the reservation time) or any timebefore the time slot of the existing reservation. This may includecanceling an existing reservation and attempting to replace it with atime slot preferred by the guest, trading an existing reservation withanother guest, canceling an existing reservation and being put in avirtual standby queue, or the like. When a guest is attempting to changean existing reservation, that guest may be given priority over guestswithout existing reservations for purposes of selection of otheravailable time slots for a replacement reservation.

Once all transfers have been made, a determination may be made regardingassociated delays or other issues with the reservations, as indicated byblock 422. This may include periodically updating and continuouslymonitoring attraction information from monitoring systems (e.g.,attraction systems 122) associated with the related attractions. Ifissues are identified that will cause changes in reservations, the guestmay be notified via text message, voice message, email, or via a kioskdisplay of a new time window for the reservation, as represented byblock 424. The notification may also include an indication of the natureof the delay or change. Further, any conflicting reservations may beautomatically adjusted. For example, if the changed reservation timeconflicts with an established reservation time, the establishedreservation time may be automatically changed or the guest may beprompted to define a desired result from a selection of availableoptions.

If no issues are identified with respect to changes in reservations, theprocess 400 may continue to monitor whether a time period before thereservation has been reached, as represented in block 430. For example,block 430 could represent a determination as to whether the current timeis 15 minutes or less prior to the reservation (e.g., a time window). Ifthe current time is not 15 minutes or less prior to the reservation, theprocess 400 continues to monitor. If the current time is 15 minutes orless prior to the reservation, the guest is provided with a reminderthat the reservation time is near, as represented by block 432. This mayinclude a suggestion that the guest begin moving toward the attraction.It should be noted that the time period before which the guest isnotified may vary depending on the location of the guest. For example,if the system 100 identifies that the guest is in a particular locationfrom which it generally takes a certain amount of time to travel to theattraction for which the guest has a reservation, the time periodassociated with the reservation reminder notification may be based onthis distance and corresponding travel time.

After receiving the reservation reminder notification, the system 100may enable a guest to move the reservation back or postpone thereservation. For example, a guest may be prompted or allowed to requesta delay in the reservation, as indicated by block 434. If the guestchooses to delay the reservation, the guest may notify the reservationsystem 100 via the mobile device or other access points to thereservation system 100, as represented by block 436. The reservationsystem 100 may respond to such a request with information regarding anew reservation at a later time, a selection of reservation times thatare available at later times, or an indication that no later times areavailable. The system 100 may then enable the guest to respond by, forexample, confirming or selecting a supplied later time or declining tochange the existing reservation. If a new reservation is established,the system 100 provides confirmation of the revised reservation, asindicated by block 438, and the process continues to monitor the currenttime relative to the reservation, as indicated by block 430. It shouldalso be noted that, at any time in the process, a guest might choose tocancel their reservation in addition to modifying it.

If the guest elects not to delay the reservation, the guest may beginwalking to the attraction, as represented by block 440. As noted above,the reservation reminder may account for the distance that will betraveled by the guest by monitoring the location of the guest andproviding a reminder a corresponding amount of time in advance of thereservation time. A determination may be made regarding when thereservation time becomes active, such as when the current time enters atime window for the reservation, as represented by block 442. This iscontinuously monitored in the illustrated embodiment. When the currenttime corresponds to the reservation (e.g., the current time is withinthe reservation window), the guest is notified that the reservation isactive and that the guest should enter the attraction, as indicated byblock 444. When the guest enters a queue associated with the attraction,the guest may be required to confirm that they have a reservation byproviding appropriate identification information, as indicated by block446. For example, the data reader 108 of the system 100 may be used toscan tickets or interface with a mobile device at the entrance to ashort reservation queue or an entry point to confirm that the guest hasa reservation.

When an initial confirmation of guest identification and reservationinformation (e.g., a ticket scan) is performed at the entrance to aqueue, further verification may be required prior to actually enteringthe attraction (e.g., boarding a ride), as represented by block 448.This may facilitate monitoring of the queue length at the associatedattraction. Future provision of reservations and access provided tostandby queues may be adjusted based on this measurement to control thewait time in the reservation queue. For example, during steadyoperation, present embodiments may control the approximate time spent byguests in a reservation queue to be around 10 minutes. Indeed, thesystem 100 may instruct an operator to allow guests to exit a queue andboard an attraction as designated intervals based on an algorithmaccounting for queue characteristics. Confirming identificationinformation (e.g., scanning a ticket and accessing associatedreservation data) for a guest entering a ride may also facilitatemonitoring and control of subsequent access to attractions. For example,this may be used to indicate that a guest has already accessed aparticular attraction using a reservation. An indication may be storedon the system 100 and associated with the identification informationsuch that subsequent requests for reservations can be controlled basedon whether certain attractions have already been accessed by the guest.This may include scanning tickets and so forth after the guests exit anattraction.

The system 100 may employ an algorithm that takes into account thatcertain guests may have accessed an attraction just prior to theattraction experiencing technical difficulties and becoming inoperable.For example, block 452 represents determining whether a guest checked into an attraction but did not get to experience the attraction due totechnical difficulties or the like. If the attraction was functional,the guest is indicated as having experienced the attraction, asrepresented by block 454. If the attraction was not functional, theguest may be automatically assigned another reservation or an immediateaccess right upon correction of the technical difficulty or the like, asrepresented by block 456. An attraction may be considered nonfunctionalwhen access to the attraction is prevented or when the attractionexperience is interrupted.

Present embodiments will allow for reservation trading via a reservationtrading system, which may be a component or module of the data serversystem 102. This functionality may be available when the system 100 isin use with multiple attractions. For example, a first guest may have areservation to access a first ride at 1:00 PM. However, the first guestmay be eating lunch and will not be able to reach the attraction in timefor this reservation. The system may prompt the first guest a certaintime (e.g., 15 minutes) prior to the reservation to determine whetherthe first guest plans to keep the reservation. The time of prompting maybe based on a detected location of the guest relative to the attraction116 for which the reservation has been established. Since the firstguest is unable to reach the first attraction in time, the first guestmay respond by indicating that the reservation is not going to be kept.The system 100 may then automatically look for a later reservation forthe first guest. A second guest may have a reservation at 4:00 PM andmay be currently located near the first attraction, as determined by thesystem 100. The system 100 may identify this second guest based onlocation and time of reservation, and send the second guest a messageindicating that a trade is available for the reservation held by thefirst guest. If the second guest accepts the trade, the reservations maybe transferred between the first and second guests by the system 100 andthe guests respectively notified of their new reservations. This assistswith maintaining full capacity while eliminating stresses on guestsassociated with making appointments on time.

Present embodiments include a process and system configured to provideeach of multiple different guests or groups with multiple reservationsor an itinerary based on input from the guests. For example, FIG. 5 is aprocess flow diagram that provides a general overview of a process 600for facilitating guest scheduling of multiple reservations forattractions ranging from rides to restaurants in accordance with presentembodiments. The process 600 of FIG. 5 generally illustratesestablishing an itinerary that substantially optimizes the guests' timein the park and the park facilities. It should be noted that the process600 is illustrated at a high level and may include the specific processfeatures discussed above with respect to FIGS. 2-4. Further, the process600 may be implemented using all or some features of the system 100discussed above.

The process 600 begins with enabling guests to communicate with areservation system and provide certain attraction preferences, asrepresented by block 602. This may include providing access to areservation system for guests inside or outside of the park. Forexample, guests may provide a list of certain attractions the guests areinterested in experiencing or types of attractions the guests areinterested in experiencing. This may include providing specificattractions and preferred times for associated reservations along with aranking indicating a level of interest in each attraction. However, theguests may choose to simply provide a list of attractions of interestand allow the system to propose times. Similarly, the guests may simplyprovide certain attraction types (e.g., rides appropriate for smallchildren) and allow the system to propose an itinerary. Once thepreferences are entered, the reservation system receives the associateddata, as represented by block 604, and then processes the data tosubstantially optimize a schedule for each guest and optimizeutilization of the park attractions, as represented by block 606. Inresponse to the preferences provided by the guests, the reservationsystem may perform an optimization algorithm and output a proposeditinerary, as represented by block 608. In one embodiment, the guest mayprovide input before entering the park but will not receive a proposeditinerary until after entering the park.

The algorithm represented as being performed in block 606 may be storedon a memory and performed by a processor of the system (e.g., aprocessor 118 of data server system 102) to produce a proposeditinerary, as represented by block 608. The guest may then confirm theitinerary or request a different itinerary after reviewing the proposeditinerary, as represented by block 610. If confirmation is received bythe system, the process provides a confirmed itinerary, as representedby block 612. If the guest elects to modify the itinerary, the guest maybe prompted to indicate whether specific modifications are requested orcancellation is desired. If cancellation is desired, the process endsand cancellation is confirmed, as represented by block 616. Ifmodifications are desired, the process may return to block 604 and/orenable changes to the schedule. It should note be noted that the systemmay provide proposed modifications based on attraction availability andrecognized limitations of the guest's preferred schedule based onoptimization data at any point in the process 600.

The algorithm represented as being performed in block 606 may functionto identify the location of the attractions listed as being of interestto the guests and determine a schedule based on a number of factors oroptimization data, such as ease of transition between individualattractions of interest. For example, the system may propose anitinerary that includes reservations for the guests' preferredattractions in a series that allows the guests to move from attractionto attraction throughout the park without requiring the guests tobacktrack. The itinerary may also include proposed reservations forattractions along the path based on gaps in the schedule. In addition totaking distances and locations of attractions into consideration, thealgorithm may consider maximization of operational efficiency of thepark, the reservations of others, levels of interest, mealtimes,overlapping schedules with other guests designated as being in a commongroup (e.g., social network), and so forth. For example, theoptimization algorithm may propose an itinerary that limits travelbetween attractions but accommodates a lack of availability ofreservations at a particular time for a highly desired attraction. Thealgorithm may also direct guests throughout the park to avoid predictedovercrowding in particular areas based on established reservations andhistoric park data. The algorithm may also take into consideration thata break would be required around a mealtime and propose reservations ata restaurant attraction or simply suggest nearby restaurants. Thealgorithm may also take certain practical matters into consideration.For example, the algorithm may adjust the itinerary to exclude certainhigh intensity attractions for a certain time period after meals. Thealgorithm may also attempt to maximize utilization of the park byproposing reservations or visits to attractions that are underutilizedat certain times. In one embodiment, the algorithm considers rankings oflevels of interest (e.g., high, medium, low) provided by guestsregarding attractions and provides an itinerary that accounts for this.For example, the algorithm may arrange reservations for attractions ofhigh interest to be spread throughout the day to keep interest upthrough the day or to all occur early in the day to make sure that allof the high interest attractions are experienced early.

Present embodiments may also facilitate group meetings within the parkfor parties that arrive separately, parties that separate once insidethe park, or parties that desire a certain overlap in scheduling. Forexample, FIG. 6 illustrates a process 700 performed in accordance withpresent embodiments for coordinating guest schedules. The process beginswith prompting the guest to indicate whether the guest would like tounite with a party of which the guest is already a member or whether theguest would like to have an itinerary that overlaps with that of anotherparty. This initial procedure is represented by block 702 and may beperformed using any of the access features discussed above with respectto the system 100, such as a cellular telephone in coordination with thesystem 100. Block 702 includes identifying the guest and the group.

If the guest wishes to meet with a group or party of which the guest isa member, the process may identify a meeting location, as represented byblock 704, and direct the guest to the location and/or instruct theparty to meet the guest at the location, as represented by block 706.This will generally occur when guests do not arrive to the park withtheir party or split off from their party during a visit. To facilitateregrouping of a party, present embodiments may utilize PIF positioninginformation to direct the guest to the desired party, use theestablished itinerary for the party to provide the meeting location, useguest-to-guest communications to communicate the meeting location,and/or use system-to-guest communications to communicate the meetinglocation. For example, the next attraction on the itinerary may beprovided to the guest and the party may be informed via a text messagethat the guest will be joining the party for the reservation at the nextattraction. Further, guest-to-guest communication may be facilitatedbetween the party and the guest via the reservation system (e.g., textmessaging or voice communications).

If the guest wishes to establish an overlap between the guest or theguest's group or party and at least one other group, the process 700proceeds to block 710 in the illustrated embodiment. This may occur whentwo or more groups or individuals decide to spend time together at thepark. For example, groups from a particular area may decide to establishoverlapping schedules so that they can experience attractions of commoninterest together while experiencing other attractions in their separategroups. The groups or individuals may already have reservations (e.g.,itineraries) or not. Block 710 generally represents identifying thegroups or individuals and confirming a desire to have overlappingattraction experiences. Once this is established, a determination ismade as to whether the one or more groups have existing itineraries orreservations, and preferences are provided where no itineraries orreservations are established, as represented in block 712. Existingitineraries and reservations are taken into consideration andpreferences are otherwise provided. This may include providingattractions of common interest and desired overlap. An algorithm is thenperformed based on common interest of the guests based on explicitdesignations, comparison of preferences, comparison of existingitineraries, and/or optimization data to provide overlapping itinerariesfor the two or more individual guests or groups of guests, asrepresented by block 714.

While only certain features of the invention have been illustrated anddescribed herein, many modifications and changes will occur to thoseskilled in the art. It is, therefore, to be understood that the appendedclaims are intended to cover all such modifications and changes as fallwithin the true spirit of the invention.

The invention claimed is:
 1. A method comprising: receiving attractionpreference data into a reservation system before a guest enters a park,wherein the attraction preference data includes an attraction listcomprising a plurality of attractions of the park selected by the guestand a guest-designated level of interest in each attraction of theplurality of attractions selected by the guest, wherein the plurality ofattractions of the park selected by the guest are attractions of thepark that the guest is interested in experiencing; analyzing theattraction preference data to produce analysis results using analgorithm performed by a processor of the reservation system, whereinthe algorithm is configured to perform the analysis using attractionavailability data generated from electronic monitoring of the pluralityof attractions associated with the attraction list, location dataassociated with the attraction list, park utilization data, and theguest-designated level of interest in the respective attractions;electronically detecting a portable identification feature associatedwith the guest at an entrance into the park using a guest entry systemof the reservation system, wherein electronically detecting the portableidentification feature comprises polling the guest entry system of thereservation system at predetermined intervals to retrieve informationindicative of detection of the portable identification feature toautomatically identify that the guest has arrived at the park, anddisplaying a proposed itinerary on the portable identification featurefor the guest to confirm, modify, or cancel in response to determiningthat the guest has entered the park, wherein the proposed itinerary isbased on the analysis results, wherein the proposed itinerary comprisesreservations for the guest, and wherein one or more of the reservationshas a specific time window for the guest to access a respectiveattraction from the attraction list; and presenting the proposeditinerary according to the analysis results, wherein the reservationsare presented in series such that the guest is guided to a series ofattractions in a manner that limits backtracking.
 2. The method of claim1, comprising initiating a reminder of the reservations at a promptingtime prior to a respective specific time window of one of thereservations, wherein the prompting time is based on a location of theguest relative to a location of the respective attraction.
 3. The methodof claim 1, wherein the algorithm is configured to perform the analyzingusing rankings of levels of interest between each attraction of theplurality of attractions of interest by the at least one user.
 4. Themethod of claim 1, wherein the algorithm is configured to perform theanalyzing using historic park data associated with the plurality ofattractions of interest.
 5. The method of claim 1, comprising assigningthe reservations having the specific time windows for accessing the oneor more attractions to the portable identification feature associatedwith the guest and to another portable identification feature associatedwith another guest.
 6. The method of claim 1, wherein presenting theproposed itinerary comprises presenting the reservations for attractionsin the attraction list designated by the guest as high interest to beinterspersed throughout the proposed itinerary such that interest of theguest is maintained throughout the duration of the proposed itinerary.7. The method of claim 1, wherein presenting the reservations accordingto the attraction preference data and the user-designated level ofinterest comprises presenting the reservations designated as highinterest early in the proposed itinerary.
 8. The method of claim 1,comprising adjusting the proposed itinerary to exclude certain highintensity attractions for a period of time following a reservation at arestaurant of the park.
 9. The system of claim 1, wherein the portableidentification feature comprises a cellular telephone.
 10. The system ofclaim 1, wherein the portable identification feature comprises awearable feature.
 11. The system of claim 10, wherein the wearablefeature comprises a bracelet having integral circuitry.
 12. A methodcomprising: receiving a request to generate an overlapping itinerary fora park between a first group of guests and a second group of guests viaa reservation system; identifying, via the processor of the reservationsystem, one or more existing itineraries for the park or preferencesrelating to the park of the first group of guests and the second groupof guests, wherein the one or more existing itineraries for the park orpreferences relating to the park comprise a first plurality ofattractions selected by the first group of guests and a second pluralityof attractions selected by the second group of guests, and wherein thefirst plurality of attractions selected by the first group of guests areattractions the first group of guests are interested in experiencing andthe second plurality of attractions selected by the group of guests areattractions the second group of guests are interested in experiencing;generating one or more overlapping itineraries for the first group ofguests and the second group of guests based on common attractionsbetween the first plurality of attractions selected by the first groupof guests and the second plurality of attractions selected by the secondgroup of guests identified via the one or more existing itineraries orpreferences, wherein the overlapping itineraries comprise reservations,each reservation having a specific time window for the first group ofguests and the second group of guests to access an attraction of thepark, wherein the reservations are presented according to attractionpreference data and a designated level of interest in one or moreattractions, wherein the designated level of interest in the one or moreattractions is provided by the first group of guests, the second groupof guests, or both, and wherein the reservations are presented in seriessuch that the first group of guests and the second group of guests areguided to a series of attractions in a manner that limits backtracking;detecting a first portable identification feature associated with thefirst group of guests and a second portable identification featureassociated with the second group of guests at an entrance to the parkusing a guest entry system of the reservation system; wherein detectingthe first portable identification feature and the second portableidentification feature comprises polling the guest entry system of thereservation system at predetermined intervals to receive data indicativeof detection of the first portable identification feature and detectionof the second portable identification to automatically identify that thefirst group of guests and the second group of guests have arrived at thepark; and displaying the overlapping itineraries to the first group ofguests on the first portable identification feature associated with thefirst group of guests when the first group of guests arrive at the parkand to the second group of guests on the second portable identificationfeature associated with the second group of guests when the second groupof guests arrive at the park.
 13. A queue management system, comprising:a reservation system including at least one processor and memory, thememory storing instructions that when executed by the at least oneprocessor, cause the reservation system to: receive attractionpreference data before a guest enters a park, wherein the attractionpreference data includes an attraction list comprising a plurality ofattractions of the park selected by the guest and a guest-designatedlevel of interest in each attraction of the plurality of attractionsselected by the guest, wherein the plurality of attractions of the parkselected by the guest are attractions of the park that the guest isinterested in experiencing; analyze the attraction list utilizing analgorithm stored in the memory to produce analysis results, wherein thealgorithm is configured to analyze the attraction list based onattraction availability data associated with the attraction list,location data associated with the attraction list, park utilizationdata, and the guest-designated level of interest in respectiveattractions in the attraction list; detect a portable identificationfeature associated with the guest using a guest entry system reservationsystem at an entrance into the park by polling the guest entry system ofthe reservation system at predetermined intervals to retrieveinformation indicative of detection of the portable identificationfeature to automatically identify whether the guest has entered thepark, wherein the portable identification feature comprises a wearablefeature; generate, in response to determining that the guest has enteredthe park, a proposed itinerary for the guest based on the analysis ofthe attraction list, wherein the proposed itinerary comprisesreservations for the guest, and wherein one or more of the reservationshas a specific time window for the guest to access a respectiveattraction from the attraction list; and display on the portableidentification feature the proposed itinerary with the reservations inseries such that the guest is guided to a series of attractions in amanner that limits backtracking.
 14. The queue management system ofclaim 13, wherein the instructions, when executed by the at least oneprocessor, cause the reservation system to notify the guest in responseto determining that a detection system of the reservation system detectsthe portable identification feature has not arrived to a particularattraction in the attraction list within a general time period ofarrival.
 15. The system of claim 13, wherein the instructions, whenexecuted by the at least one processor, cause the reservation system tomonitor wait times of a queue for any one of the attractions in theattraction list in response to detecting the presence of the portableidentification feature at an entry to the one of the attractions in theattraction list and after detecting the presence of the portableidentification feature at an entry into the queue for the one of theattractions.
 16. The queue management system of claim 13, wherein theinstructions, when executed by the at least one processor, cause thereservation system to allow or deny access to attractions in the parkusing the portable identification feature and based on a number of timesthe portable identification feature has been used to access a respectiveattraction in the attraction list relative to a threshold for repeatedaccess to the respective attraction.
 17. The queue management system ofclaim 13, wherein the instructions, when executed by the at least oneprocessor, cause the reservation system to send a reminder of arespective reservation of the one or more reservations to the guest at aprompting time prior to the respective specific time window of thereservation, wherein the prompting time is based on a location of theguest relative to a location of the attraction corresponding to thereservation.
 18. A queue management system comprising: a reservationsystem including at least one processor and memory storing code that isexecutable by the at least one processor; an interface system of thereservation system configured to enable a guest to interface with atleast a portion of the reservation system to enter a reservation requestrelating to a plurality of attractions of a park before the guestarrives at the park, and to receive the reservation request, wherein theinterface system is configured such that the reservation requestreceived by the interface system includes a guest-designated arrivalperiod indicating a general time window during which the guest expectsto arrive to the park, attraction preference data including anattraction list of specific attractions selected by the guest and aguest-designated level of interest in a specific attraction from theattraction list, and identification information associated with aportable identification feature of the guest, wherein the attractionlist of specific attractions selected by the guest includes attractionsthat the guest is interested in experiencing; a reservation rightallotment module stored in the memory of the reservation system, whereinthe reservation allotment module is configured to set aside areservation slot associated with the general time window for the guestfrom an inventory having a limited number of available reservation slotsassociated with the general time window, wherein the reservation slotconfirms access for the guest to at least one specific attraction duringthe general time window without establishing a particular hourly timefor the confirmed access, and wherein the reservation right allotmentsystem is configured to associate the reservation slot with the portableidentification feature; a detection module stored in the memory of thereservation system, wherein the detection module is configured toelectronically detect the portable identification feature associatedwith the guest at an entrance to the park to automatically identifywhether the guest has arrived to the park; and a reservation assignmentmodule stored in the memory of the reservation system, wherein thereservation assignment module is configured to convert the reservationslot into a reservation having a specified hourly time at which theguest has confirmed access to the specific attraction, the specifiedhourly time being narrower than the general time window, wherein thereservation assignment module is configured to convert the reservationslot into the reservation in response to the reservation systemdetecting the portable identification feature, and wherein thereservation assignment module is configured to display the reservationon the portable identification feature associated with the guest inresponse to the detection system detecting the portable identificationfeature.
 19. The system of claim 18, wherein the interface system isconfigured such that the guest-designated arrival period is the morningor the afternoon of a particular date.
 20. The system of claim 18,wherein the reservation system is configured to: produce a proposeditinerary on the portable identification feature in response todetecting the portable identification feature, wherein the proposeditinerary is produced according to an algorithm that uses at least thereservation slot, an actual time at which the portable identificationfeature is detected, the attraction preference data, and electronicmonitoring of specific attractions in the attraction list as inputs, andwherein the proposed itinerary includes a plurality of reservations,each reservation of the plurality of reservations having a specific timewindow during which the guest has confirmed access to a respectiveattraction from the attraction list; and enable the guest to confirm,modify, or cancel the proposed itinerary.